Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GitHub Actions #20

Merged
merged 19 commits into from
Aug 30, 2020
Merged

Conversation

asbjornu
Copy link
Collaborator

@asbjornu asbjornu commented Jun 27, 2020

This PR adds a GitHub Actions workflow that performs extensive tests on the parsing of .remarkrc in preparation for a fix for #15. Without a continuous integration system with automatic tests, it's hard to debug and fix problems. This PR tries to remedy that.

The PR also upgrades the entire extension to be on par with the current Yeoman template, which was the only way I was able to get the automatic tests to work.

I can also warmly recommend that you set up Dependabot to keep all dependencies in this extensions up to date. It's free and creates pull requests with changes to package.json and package-lock.json whenever a dependency has a new version. It's also highly configurable so you can ignore minor versions, major versions, whole packages, etc.

@asbjornu asbjornu force-pushed the feature/github-actions branch from 7821b88 to b749c0d Compare August 28, 2020 08:48
@asbjornu
Copy link
Collaborator Author

@mrmlnc, this is now rebased against the HEAD of master. I would appreciate if this could be merged. 🙏

@mrmlnc
Copy link
Collaborator

mrmlnc commented Aug 29, 2020

I gave you the rights to manage the repository (includes merge of PR's).

@asbjornu asbjornu merged commit 22ae893 into remarkjs:master Aug 30, 2020
@asbjornu asbjornu deleted the feature/github-actions branch August 30, 2020 22:56
@asbjornu
Copy link
Collaborator Author

Excellent, thanks, @mrmlnc. If you want me to follow up on remarkjs/remark#508 (comment), perhaps you can make me an admin of the repository? Seeing how I'm going to have that after the repository is moved anyway, I might as well have it now, no?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants